Subject: Correction to appnNodeLsStatusXidByteInError, ...BitInError

From: "R.E. (Robert) Moore (254-4436)" <[email-masked]>
Date: Mon, 23 Oct 95 08:24:48 EDT

Since both of these objects include the n/a value as a named number,
they end up allowing *only* the n/a value in the object.  Additionally,
the byte in error object is unclear about whether the n/a value is
0 or 1000.

Suggested replacements:

appnNodeLsStatusXidByteInError      OBJECT-TYPE
      SYNTAX INTEGER (0..255)
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "This object identifies the actual byte in the XID that caused
          the error.  The value 255 indicates that the object has no
          meaning."

      ::=  { appnNodeLsStatusEntry 13 }

appnNodeLsStatusXidBitInError      OBJECT-TYPE
      SYNTAX INTEGER (0..8)
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "This object identifies the actual bit in error (0 through 7)
          within the errored byte of the XID.  The value 8 indicates that
          this object has no meaning."

      ::=  { appnNodeLsStatusEntry 14 }